Skip to content

Conversation

@philsttr
Copy link
Collaborator

@philsttr philsttr commented Nov 7, 2021

Previously, masking of a single value would stop after the first ValueMasker returned a masked value.
This meant that only one ValueMasker would process a string.
Now, all ValueMaskers are given the opportunity to process a value, which means that multiple substrings can be masked independently by different ValueMaskers

Fixes #690

Previously, masking of a single value would stop after the first ValueMasker returned a masked value.
This meant that only one ValueMasker would process a string.
Now, all ValueMaskers are given the opportunity to process a value, which means that multiple substrings can be masked independently by different ValueMaskers

Fixes #690
@philsttr philsttr requested a review from brenuart November 7, 2021 19:08
Copy link
Collaborator

@brenuart brenuart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks ok to me.
Maybe add a note in the README + changelog about actual behaviour when multiple masks are configured.

@philsttr philsttr added this to the 7.0 milestone Nov 7, 2021
@philsttr philsttr added type/bug warn/api-change Breaking change with compilation or xml configuration errors labels Nov 7, 2021
@philsttr philsttr merged commit f568823 into main Nov 7, 2021
@philsttr philsttr deleted the masked_substrings branch November 7, 2021 21:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type/enhancement warn/api-change Breaking change with compilation or xml configuration errors

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Only first ValueMasker is applied

3 participants